Starting and Quitting WinDbg
After you
have installed WinDbg, you can start it by selecting it from the Start menu.
You can also start WinDbg from the command line by typing
windbg [-a] [-g] [-h] [-i] [-k[platform port speed]]
[-l[text]] [-m] [-p id [-e event]] [-s[pipe]] [-v]
[-w name ] [-y path] [-z crashfile] [filename[.ext]
[arguments]]
The following
table describes the command-line options.
|
Option |
Description |
|
-a |
Ignore all
bad symbols (but still print warning message). |
|
-g |
Go now;
start executing the process. |
|
-h |
Causes
child processes to inherit access to WinDbg s handles. |
|
-i |
Ignore
workspace; like running without any registry data. |
|
-k [platform port speed] |
Run as a
kernel debugger with the specified options: |
|
-l [text] |
Sets the
window title for WinDbg. |
|
-m |
Start
WinDbg minimized. |
|
-p id |
Attach to
the process with the given id. |
|
-e event |
Signal an
event after process is attached. Used only for post-mortem debugging
(AeDebug). |
|
-s [pipe] |
Start a
remote .EXE server, using the named pipe. |
|
-v |
Verbose
option; WinDbg prints module load and unload messages. |
|
-w name |
Load the
named workspace. |
|
-y path |
Search for
symbols along the specified path. You can specify multiple paths by
separating them with semicolons. |
|
-z crashfile |
Debug the
specified crash dump file. |
|
filename[.ext] |
Program to
debug or file to edit. If no extension is specified, WinDbg assumes an .EXE
extension. If the file is not an .EXE or .COM file, WinDbg will try to load
it as a text file. |
|
arguments |
Arguments
to program being debugged. |
To quit
WinDbg, choose Exit from the File menu.